Skip to content

Backport of docs: KV tutorial becomes usage doc into release/1.16.x#20996

Closed
hc-github-team-consul-core wants to merge 2 commits intorelease/1.16.xfrom
backport/docs/tutorial-refresh-support/yearly-integral-clam
Closed

Backport of docs: KV tutorial becomes usage doc into release/1.16.x#20996
hc-github-team-consul-core wants to merge 2 commits intorelease/1.16.xfrom
backport/docs/tutorial-refresh-support/yearly-integral-clam

Conversation

@hc-github-team-consul-core
Copy link
Copy Markdown
Collaborator

Backport

This PR is auto-generated from #20994 to be assessed for backporting due to the inclusion of the label backport/1.16.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@boruszak
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: POST https://api.github.com/repos/hashicorp/consul/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.


Description

This PR is a minor change to support the Consul Tutorial Refresh.

When testing redirects, we noticed a circular loop: the deprecated KV store tutorial redirected to the KV overview page, but the KV overview page linked to the tutorial for its usage info.

We had already made a docs version of the tutorial for the docs refresh, so we're adding it to the docs now and fixing the redirect in the tutorials repo to create a less frustrating experience.

Deployment preview

PR Checklist

  • updated test coverage
  • external facing docs updated
  • appropriate backport labels added
  • not a security concern

Overview of commits

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto approved Consul Bot automated PR

@hashicorp-cla-app
Copy link
Copy Markdown

hashicorp-cla-app bot commented Apr 18, 2024

CLA assistant check

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes


1 out of 2 committers have signed the CLA.

  • boruszak
  • temp

temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA.
If you have already a GitHub account, please add the email address used for this commit to your account.

Have you signed the CLA already but the status is still pending? Recheck it.

* Add KV store usage page

* nav typo
@boruszak
Copy link
Copy Markdown
Contributor

#21006

@boruszak boruszak closed this Apr 22, 2024
auto-merge was automatically disabled April 22, 2024 17:55

Pull request was closed

@github-actions github-actions bot deleted the backport/docs/tutorial-refresh-support/yearly-integral-clam branch August 29, 2025 06:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants